-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Python 3.10 #6079
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Codecov Report
@@ Coverage Diff @@
## master #6079 +/- ##
=======================================
Coverage 93.31% 93.31%
=======================================
Files 102 102
Lines 30062 30062
Branches 2690 2690
=======================================
Hits 28053 28053
Misses 1833 1833
Partials 176 176
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Backport to 3.8: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply 02bb200 on top of patchback/backports/3.8/02bb2009cda3814c5cbaddc5b4a466bd0067dbdc/pr-6079 Backporting merged PR #6079 into master
🤖 @patchback |
💔 Backport was not successfulThe PR was attempted backported to the following branches:
|
Backport to 3.8: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply 02bb200 on top of patchback/backports/3.8/02bb2009cda3814c5cbaddc5b4a466bd0067dbdc/pr-6079 Backporting merged PR #6079 into master
🤖 @patchback |
Backport to 3.8: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply 02bb200 on top of patchback/backports/3.8/02bb2009cda3814c5cbaddc5b4a466bd0067dbdc/pr-6079 Backporting merged PR #6079 into master
🤖 @patchback |
(cherry picked from commit 02bb200)
What do these changes do?
Add support for Python 3.10: Trove classifier and create binary wheels for 3.10.
Are there changes in behavior for the user?
No.
Related issue number
No, a follow on from PR #5927.
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.